Payment transactions using an augmented reality device

ABSTRACT

A system and method of performing a payment transaction in an augmented user experience displayed to a user of an augmented reality device. The system includes receiving a request for user authentication from a user, authenticating the user for performing payment transactions via a merchant application executed on the augmented reality device, receiving a request for payment to a merchant for an item offered for sale to the user in an augmented environment presented by the merchant application, processing payment in the payment amount between a payment account of the user and a merchant account, wherein the request for payment is performed without the user exiting the merchant application.

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.15/858,851 filed Dec. 29, 2017, issued as U.S. Pat. No. 11,037,116, onJun. 15, 2021, and is incorporated herein by reference it its entirety.

FIELD

The embodiments discussed herein are related to systems and methods ofperforming payment transactions initiated via an augmented realitydevice.

BACKGROUND

Various augmented reality (AR) systems have recently become available.The devices offer a live direct or indirect view of a real-worldenvironment which is “augmented” or modified with computer-generated orextracted real-world sensory input elements to provide a mixed realityexperience. Some types of display systems provide a view through theseoptics so that the computer-generated elements are displayed or overlaidto the real-world view. As such, augmented reality is used to enhance orsimulate environments and to provide an enriched experience for a user.

With the increase in the number of devices or systems capable ofperforming AR, there has been a corresponding increase with the numberof applications which utilize the new technology. Specifically, althoughaugmented reality was initially used in entertainment or gamingapplications, more businesses have developed applications or programsfor AR systems.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments will be described and explained with additionalspecificity and detail through the use of the accompanying drawings inwhich:

Figure 1 illustrates an example of a system for performing paymenttransactions using an augmented reality device according to someembodiments of the present disclosure.

FIG. 2A shows a perspective view of an augmented reality device capableof performing some embodiments of the present disclosure;

FIG. 2B is a block diagram of the augmented reality device of FIG. 2A;

FIG. 3A is a block diagram of a method of performing paymenttransactions using an augmented reality device according to oneembodiment of the present disclosure;

FIG. 3B is a block diagram of another method of performing paymenttransactions using an augmented reality device according to anotherembodiment of the present disclosure;

FIG. 4 is a perspective view of an augmented reality experience and useof a merchant application according to one embodiment of the presentdisclosure;

FIGS. 5A-5D are examples of a virtual user interface which may bedisplayed to a user within a merchant application operating on anaugmented reality device according to some embodiments of the presentdisclosure;

FIGS. 6A-6B illustrate a series of user gestures which may be capturedby an augmented reality device in accordance with some embodiments ofthe present disclosure; and

FIG. 7 illustrates an example computing system that may be used in asystem configured to provide payments initiated in an augmented realitydevice.

DESCRIPTION OF EMBODIMENTS

FIG. 1 illustrates a block diagram of a networked system 100 which maybe used in making a payment through an augmented reality (AR) deviceaccording to some embodiments of the present disclosure. The system 100includes a client AR device 110, a user electronic device 180, and apayment service provider 150 in communication with the client AR device110 and the electronic device 180 over a network 102. The paymentservice provider 150 may be maintained by a payment provider or otherfinancial system, an online bank or payment system that supports moneytransfers in an online or traditional paper payment system.Alternatively, the payment service provider 150 may be maintained by acombination of service providers in different embodiments.

The network 102, in one embodiment, may be implemented as a singlenetwork or a combination of multiple networks. For example, in variousembodiments, network 102 may include the cloud, the Internet and/or oneor more intranets, landline networks, wireless networks, and/or otherappropriate types of communication networks. In another example, thenetwork may comprise a wireless telecommunications network (e.g.,cellular phone network) adapted to communicate with other communicationnetworks, such as the Internet.

The client AR device 110, in one embodiment is described more fullybelow, and may be implemented with any appropriate combination ofhardware and/or software configured for wired and/or wirelesscommunication over network 102. For example, client AR device 110 may beimplemented as an AR device individually owned by a user or as a deviceowned and operated by a merchant which enables a plurality of users aspotential clients to utilize the client AR device 110 in a retailsetting. The AR device 110 is in communication with network 102.Specific examples of various client AR devices 110 that may be used inassociation with the embodiments recited herein are described more fullybelow but it should be appreciated that, in various embodiments, theclient AR device 110 may be referred to as a user device or acustomer/client device without departing from the scope of the presentdisclosure.

The AR client device 110, in one embodiment, may include one or morebrowser applications 120 which may be used to provide a user interfaceto permit user 140 to browse information available over network 102. Forexample, browser application 120 may be implemented as a web browser toview information available over network 102. In one implementation, thebrowser application 120 comprises a software program, such as agraphical user interface (GUI), executable by a processor that isconfigured to interface and communicate with merchant services and thepayment provider 150 via network 102. In one embodiment, the user 140 isable to access a portal to the payment provider 150 via a web browserwhich accesses a webpage operated by the payment provider 150 in orderto authorize the client AR device for making purchases within a merchantapp 115.

As may be understood, a variety of different techniques of providinguser authorization via the web browser 120 may be used, including theuser 140 providing a user name, password, or other login information tothe payment provider 150. Alternatively or in addition, otherauthentication processes may be performed via the web browser 120 of theclient AR device, such as answering a security question, or any othersuitable security and/or identity verification that is available via aweb browser.

The user 140, through the client AR device 110, may also communicatewith payment provider 150 to create an account, enter credit card orother banking information, and to generally enable the process of makingpayments to a merchant using the merchant app 115.

The client AR device 110, includes a merchant app or application 115,which, in one or more embodiments, may be configured to provide an ARexperience to the user 140. As such, the merchant app may use arendering system or any other suitable system, apparatus, device,application, etc., such as those described more fully below, forpresenting augmented reality elements to the user 140 in the ARexperience and to enable the user for selecting items for purchase andmaking payments with payment provider server 150 using a user account ofthe financial system. In some embodiments, the merchant app 115 may alsoinclude a software development kit (SDK) app that may be provided by thepayment provider, which can be installed or downloaded into the merchantapp 115. The SDK app allows user 140 to make a one-touch payment throughthe merchant app 115 of the client AR client device 110, withoutrequiring the user 140 to exit the merchant app 115.

In some embodiments, the user 140 may use an additional device, such asa electronic device 180 to perform the user authentication describedmore fully below. The electronic device 180 may be maintained by one ormore wireless service providers offering voice and/or data communicationservices to the user 140 via a communication unit 190. The communicationunit 190 may also be configured to facilitate communications with thepayment provider 150 via the network 102. The electronic device 180, mayinclude storage 185 that stores user account information, such as userlogin information and/or authentication information such as a thumbprintauthentication information, facial recognition information, passcodes,passwords, and the like. In some embodiments, this authenticationinformation may be used to provide a payment authentication 195 to thepayment provider 150. In some instances, this may be performed via aninternet or network browser operating on the electronic device 180.Alternatively, the payment authentication information 195 may beperformed via a payment app of the payment provider 150 operating on theelectronic device. In some instances the payment app may also enable theuser to provide credit card or other banking information or to monitorpayments which have been authorized by the user account of the user 140,check balances, or perform other processes of a mobile banking app.

The payment provider 150, in one embodiment, may be maintained by anonline payment system, which may provide processing for financialtransactions on behalf of user 140 with a merchant. The payment provider155 includes one or more payment applications 155 which may beconfigured to interact with the client AR device 110 and/or theelectronic device 180 over the network 102 to facilitate the purchase ofgoods or services, communicate/display information, and make payments byuser 140 of the client AR device 110 and as discussed herein.

The payment provider 150 maintains a number of user accounts 160,including a user account described more fully below associated with theuser 140 and a merchant account associated with a merchant operating themerchant app 115, each of which may include account information 165associated with individual users. For example, account information 165may include financial information of users of devices such as accountnumbers, passwords, device identifiers, user names, phone numbers,credit card information, bank information, or other financialinformation which may be used to facilitate payment transactions by andbetween users, such as user 140 and the merchant. In some embodiments,the payment application 155 may be configured to interact with theelectronic device 180 to request payment authentication from the user140 during a transaction through merchant app 115 for a payment using anaccount of the user 140, which is associated with the electronic device180.

A transaction processing application 170, which may be part of paymentapplication 155 or separate, may be configured to receive informationfrom the client AR device 110 and/or electronic device 180 forprocessing and storage in a payment database 175. Transaction processingapplication 170 may include one or more applications to processinformation from user 140 for processing an order and payment asdescribed herein. Payment application 155 may be further configured todetermine the existence of and to manage accounts for user 140, as wellas create new accounts if necessary, including obtaining user deviceinformation, such as a phone number of the electronic device 180associated with an account.

FIG. 2A shows a perspective view of a wearable “AR” device 200, which isan example of the client AR device 110 of FIG. 1 , from the perspectiveof a user 140 of the device 200. In this example, FIG. 2A is aMICROSOFT® Hololens augmented reality device, although it should beappreciated that any other suitable augmented reality devices may beused without departing from the scope of the present disclosure. Assuch, other headpieces are also within the scope of the subject matter.For instance, the display optics can equally be attached to the usershead using a frame (in the manner of conventional spectacles), helmet orother fit system.

FIG. 2B shows a schematic block diagram of the AR device 200. The ARdevice 200 is a computer device in the form of a wearable headset. Theuser 140 is not shown in FIGS. 2A and 2B, but is depicted in some of thelater figures.

The AR device 200 includes a headpiece 203, which is a headband,arranged to be worn on the wearer's head. The headpiece 203 has acentral portion 204 intended to fit over the nose bridge of a wearer,and has an inner curvature intended to wrap around the wearer's headabove their ears.

The headpiece 203 supports left and right optical components, labelled210L and 210R, which may be waveguides. For ease of reference herein anoptical component 210 may be considered to be either a left or rightcomponent, because the components are essentially identical apart frombeing mirror images of each other. Therefore, all description pertainingto the left-hand component also pertains to the right-hand component.The central portion 204 houses at least one light engine 217, depictedin FIG. 2B.

The light engine 217 comprises a micro display and imaging optics in theform of a collimating lens (not shown). The micro display can be anytype of image source, such as liquid crystal on silicon (LCOS) displays,transmissive liquid crystal displays (LCD), matrix arrays of LED's(whether organic or inorganic) and any other suitable display. Thedisplay is driven by circuitry which is not visible in FIGS. 2A and 2Bwhich activates individual pixels of the display to generate an image.Substantially collimated light, from each pixel, falls on an exit pupilof the light engine 217. At the exit pupil, the collimated light beamsare coupled into each optical component, 210L, 210R into a respectivein-coupling zone 212L, 212R provided on each component. In-coupled lightis then guided, through a mechanism that involves diffraction and totalinternal reflection (TIR), laterally of the optical component in arespective intermediate (fold) zone 214L, 214R, and also downward into arespective exit zone 216L, 216R where it exits the component 210 towardsthe users' eye. The optical component 210 is located between the lightengine 217 and the eye i.e. the display system configuration is ofso-called transmissive type.

The collimating lens collimates the image into a plurality of beams,which form a virtual version of the displayed image, the virtual versionbeing a virtual image at infinity in the optics sense. The light exitsas a plurality of beams, corresponding to the input beams and formingsubstantially the same virtual image, which the lens of the eye projectsonto the retina to form a real image visible to the user 140. In thismanner, the optical component 210 projects the displayed image onto thewearer's eye. The optical components 210L, 210R and light engine 217constitute display apparatus of the AR device 200.

The zones 212, 214, 216 can, for example, be suitably arrangeddiffractions gratings or holograms. The optical component 210 has arefractive index n which is such that total internal reflection takesplace to guide the beam from the light engine along the intermediateexpansion zone 214, and down towards the exit zone 216.

The optical component 210 is substantially transparent, whereby thewearer can see through it to view a real-world environment in which theyare located simultaneously with the projected image, thereby providingan augmented reality experience.

To provide a stereoscopic image, i.e. that is perceived as having 3Dstructure by the user, slightly different versions of a 2D image can beprojected onto each eye for example from different light engines 217(i.e. two micro displays) in the central portion 204, or from the samelight engine (i.e. one micro display) using suitable optics to split thelight output from the single display.

The wearable AR device 200 shown in FIG. 2A is just one exampleconfiguration. For instance, where two light-engines are used, these mayinstead be at separate locations to the right and left of the device(near the wearer's ears). Moreover, whilst in this example, the inputbeams that form the virtual image are generated by collimating lightfrom the display, an alternative light engine based on so-calledscanning can replicate this effect with a single beam, the orientationof which is fast modulated whilst simultaneously modulating itsintensity and/or color. A virtual image can be simulated in this mannerthat is equivalent to a virtual image that would be created bycollimating light of a (real) image on a display with collimatingoptics. Alternatively, a similar AR experience can be provided byembedding substantially transparent pixels in a glass or polymer platein front of the wearer's eyes, having a similar configuration to theoptical components 210A, 210L though without the need for the zonestructures 212, 214, 216.

The AR device 200 also comprises one or more cameras 219—stereo cameras210L, 210R mounted on the headpiece 203 and configured to capture anapproximate view (“field of view”) from the user's left and right eyesrespectfully in this example. The cameras are located towards eitherside of the user's head on the headpiece 3, and thus capture images ofthe scene forward of the device form slightly different perspectives. Incombination, the stereo camera's capture a stereoscopic moving image ofthe real-world environment as the device moves through it. Astereoscopic moving image means two moving images showing slightlydifferent perspectives of the same scene, each formed of a temporalsequence of frames to be played out in quick succession to replicatemovement. When combined, the two images give the impression of moving 3Dstructure.

As illustrated in FIG. 2B, the AR device 200 may also comprise: one ormore loudspeakers 211; one or more microphones 213; memory 205;processing apparatus in the form of one or more processing units 203(e.g. CPU(s) 235, GPU(s) 237), and/or bespoke processing units optimizedfor a particular function, such as AR related functions); and one ormore computer interfaces or a communications module 240 forcommunication with other computer devices, such as using a Wifiinterface 207 a, Bluetooth interface 207 b, and the like. The AR device200 may comprise other components that are not shown, such as dedicateddepth sensors, additional interfaces etc.

As illustrated in FIG. 2A, a left microphone 211L and a right microphone213R are located at the front of the headpiece (from the perspective ofthe wearer), and left and right channel speakers, earpiece or otheraudio output transducers are to the left and right of the headpiece 203.These are in the form of a pair of bone conduction audio transducers2111, 211R may function as left and right audio channel output speakers.

Additionally, although not externally visible, the processing unit 230,memory 205 and interfaces 207 a, 207 b may be housed in the headpiece203. Alternatively, these may be housed in a separate housing connectedto the components of the headpiece 203 by wired and/or wireless means.For example, the separate housing may be designed to be worn or a beltor to fit in the wearer's pocket, or one or more of these components maybe housed in a separate computer device (smartphone, tablet, laptop ordesktop computer etc.) which communicates wirelessly with the displayand camera apparatus in the AR headset 200, whereby the headset andseparate device constitute augmented reality apparatus.

The memory 205 holds executable code that the processing using 230 isconfigured to execute. In some cases, different parts of the code may beexecuted by different processing units of the processing unit 230. Thecode may comprise code of an operating system, as well as code of one ormore applications configured to run on the operating system.

FIG. 3A is a block diagram illustrating a method 300 of performing apayment transaction in an augmented user experience displayed to theuser 140 of the client AR device 110 according to one embodiment. Inthis embodiment, the method begins at 302 in response to the paymentprovider 150 receiving a request for user authentication from the user140. The user authentication may include a variety of informationincluding a user identifier uniquely associated with a payment accountof the user 140 at the payment provider 150 in addition to a password orother user verification information using a log-in web portal or otherwebsite provided by the payment provider 150. In some instances, theuser 140 may create a user account at the payment provider during thisprocess, and may select the unique user identifier and provider paymentinformation to the payment provider 150 via the web browser 120.

In response to receiving the request for user authentication, thepayment provider 150 may authenticate 304 the user for performingpayment transactions on the client AR device 110. In response to theuser 140 being authenticated for performing payment transactions on theclient AR device 110, the user 140 may interact with the merchantapplication in an AR experience. During this experience, as is describedmore fully below, the user 140 may be presented with various items forsale by the merchant enabling the user to browse through the variety ofitems in an augmented reality experience.

In response to the user 140 selecting an item for purchase, a requestfor payment is transmitted to the payment provider 150 via the client ARdevice 110. In some instances, as described above, this request forpayment may be transmitted by a software development kit (SDK) installedin or operating in association with the merchant application 115 withoutthe user 140 having to exit the merchant application 115. At 306, thepayment provider receives the request for payment to the merchant forthe selected item offered for sale to the user 140. The request forpayment includes a unique merchant identifier and a payment amount. At308, the payment provider 150 identifies a merchant account associatedwith the unique merchant identifier, and at 310 a payment in the paymentamount is performed between the payment account of the user and themerchant account.

FIG. 3B illustrates an alternative embodiment of a method 350 forperforming a payment transaction in an augmented user experiencedisplayed to the user 140 of the client AR device 110. In thisembodiment, the user 140 selects items for purchase using the client ARdevice 110, but performs purchase authentication through a secondaryelectronic device 180. More particularly, the method begins at 352 inresponse to the payment provider 150 receiving a request for paymenttransmitted to the payment provider 150 via the client AR device 110. Insome instances, as described above, this request for payment may betransmitted by a software development kit (SDK) installed in oroperating in association with the merchant application 115 withoutrequiring the user 140 to exit the merchant application 115. The requestfor purchase includes the unique user identifier, a unique merchantidentifier, and a payment amount.

In response to receiving the payment request, the payment provider 150transmits a request for authentication to a electronic device 180associated with a user account associated with the unique useridentifier. In some instances, this may involve a notification sent tothe electronic device via a text, phone call, notification, email,alert, or communication requesting that the user authenticate thepurchase. This authentication may be performed via a number of differentmechanisms such as via a thumbprint, authorizing password, passcode,predetermined pattern, text/email response, facial recognition, or thelike.

Based on the authentication response being determined to be valid, at358 the payment provider 150 authenticates the payment. At 360, thepayment provider 150 identifies a merchant account associated with theunique merchant identifier, and at 362 a payment in the payment amountis performed between the payment account of the user and the merchantaccount.

By using multiple devices, the method described in FIG. 3B enables auser to select items for purchase using the AR client device 110 whilethe user 140 is interacting with the augmented reality and thensubsequently or even in some instances simultaneously use another device180 to easy authorize the payment. Such a mechanism provides theadvantages offered by each device without requiring the user 140 toattempt to enter in the authenticating information via the client ARdevice 110. Additionally, such systems may provide additional securityto the users 140 and the ability to monitor the purchase once the ARexperience has been completed.

FIG. 4 is an example of an AR experience 410 which may be presented tothe user 140 via a merchant application 115. In this embodiment, theuser 140 uses the client AR device 110 to visualize a variety of homefurniture that may be offered for sale by a merchant in his or her ownphysical home or as a simulation in a display room. For example, byusing the AR device 110, the user is able to add or remove furniturefrom a selection of available items to a physical room so as to see apreview or a demonstration of how the furniture would look in his or herown home. In this instance, the user 140 has selected a variety of homefurniture, including a couch 415, a lamp 425, and a framed picture 420which are shown as AR elements projected onto a real-world physical room450. As the user 140 browses using the merchant app 115, furniture orother items offered for sale may be quickly and easily added, moved, orremoved according to the user's preferences, saving the user 140extensive time and energy that would be involved if the actual physicalfurniture corresponding to the AR elements were actually physicallyadded, removed, or removed from the user's home or office. As the user140 interacts with the merchant app 115, items are added to a virtualshopping cart, shown as element 470. As may be understood, any number ofgestures or actions may be used in association with the client AR device110 and merchant app 115 in enabling the user 140 to add, remove, ormove the AR elements to the AR experience 110, such as capturing usergestures, audio instructions, and the like.

FIGS. 5A-5D show examples of user interface 500 which may be presentedto the user 140 via the AR client device 110 to enact the purchase ofthe items offered for sale which have been selected by the user 140 forpurchase. FIG. 5A illustrates a shopping cart 510 that includes alisting of items which have been selected for purchase and a totalpurchase amount for the sum of the price for each of the selected items.The user interface also includes a “buy now” button, which may beselected to initiate the payment process and a “Keep Shopping” button,which, in response to being selected enables the user 140 to continueshopping via the merchant app 115.

FIGS. 6A-6B illustrate an example of the mechanism for capturing a usergesture in accordance with the client AR device 110. As was previouslydescribed above, the AR device 110, shown here as the headset 200 has aseries of cameras for capturing user movement as the user interacts inthe AR experience 600. More specifically, in this instance, as the usermoves his or her arm 650, the client AR device 110 captures the movementvia the cameras and then determines that the user is selecting aparticular box, window, or other element displayed to the user 140 inthe AR experience 600. In FIG. 6B, as the user closes his hand 655, theuser is determined to be selecting the box at the location correspondingto the AR element shown to the user 140 in the AR experience 600.

In a similar manner, the client AR device 110 may enable the user 140 toinput other information such as the user identifier, password, or thelike.

In other embodiments, other means for selection may be used, such asusing the microphone client AR device 110 for enabling the user to inputinformation via the microphone, which information is then captured andconverted into text or other digital information.

By using this or other selection mechanisms, at FIG. 5B the user isdetermined to have clicked or selected the “Buy Now” box 515. Inresponse to this selection, the user 140 is then presented with a seriesof payment options, such as manually entering payment info such ascredit card information via the selection of box 530. In some instances,where the user 140 has already authenticated the purchase(s) via theclient AR device 110, the user 140 may easily authorize the payment byselecting the “Pay Now” button and no further authorization may berequired by the payment provider 150 to process the payment from theuser to the merchant. In some instances, the “Pay Now” button 535 mayonly be displayed to the user 140 after the user has already authorizedthe client AR device 110 for performing purchases.

In instances where the user 140 has not previously authorized the clientAR device 110 for purchases, the user 140 may log into the paymentsystem by selecting box 540, in response to which the user interface maydisplay screen 565 for enabling the user 140 to enter a user identifier555 and password 560. As was previously described, this may be performedvia an audio response captured by the microphones 213 of the AR device200, via gestures or movement captured by cameras 218 of the AR device200 or other input means.

As such, embodiments described herein provide a mechanism which enablethe user 140 not only interact with AR elements within an AR experienceprovided by the AR client 110, but also enable the user 140 to initiatepayment for a selection of items while still within the AR experienceprovided by the merchant app 115. As may be understood, this makes iteasier for the user to directly correlate the selection of items withthe ability to purchase the items rather than simply providing the userwith a physical shopping list of items which the user must then reselectfor purchase using an alternate means. Furthermore, this provides abenefit to the merchant providing the merchant app 115 since theimproved ease at which users may purchase items results in additionalsales and an increased incentive to using the merchant app 115 andclient AR device 110.

In association with the embodiments described herein, FIG. 7 illustratesan example computing system 700 (“system 700”) that may be used in asystem configured to perform purchases made via the client AR device110, in accordance with one or more embodiments of the presentdisclosure. The system 700 may include a processor 710, a memory 720,data storage 730, and a communication unit 740, which all may becommunicatively coupled. In some embodiments, at least a portion of thesystem 700 may be part of any of the systems or devices described inthis disclosure. For example, For example, the system 700 may beincluded in or part of the elements 110, 150, and 180 of FIG. 1 .

Generally, the processor 710 may include any suitable special-purpose orgeneral-purpose computer, computing entity, or processing deviceincluding various computer hardware or software modules and may beconfigured to execute instructions stored on any applicablecomputer-readable storage media. For example, the processor 710 mayinclude a microprocessor, a microcontroller, a digital signal processor(DSP), an application-specific integrated circuit (SIC), aField-Programmable Gate Array (FPGA), or any other digital or analogcircuitry configured to interpret and/or to execute program instructionsand/or to process data.

Although illustrated as a single processor in FIG. 7 , it is understoodthat the processor 710 may include any number of processors distributedacross any number of networks or physical locations that are configuredto perform individually or collectively any number of operationsdescribed herein. In some embodiments, the processor 710 may interpretand/or execute program instructions and/or process data stored in thememory 720, the data storage 730, or the memory 720 and the data storage730. In some embodiments, the processor 710 may fetch programinstructions from the data storage 730 and load the program instructionsinto the memory 720.

After the program instructions are loaded into the memory 720, theprocessor 710 may execute the program instructions. In these and otherembodiments, the payment processing steps of the methods describedherein may be stored in the memory 720 and/or the data storage 730 andmay be loaded and executed by the processor 710 to perform operationswith respect to the AR device based transaction.

The memory 720 and the data storage 730 may include computer-readablestorage media or one or more computer-readable storage media forcarrying or having computer-executable instructions or data structuresstored thereon. Such computer-readable storage media may include anyavailable media that may be accessed by a general-purpose orspecial-purpose computer, such as the processor 710. By way of example,such computer-readable storage media may include non-transitorycomputer-readable storage media including Random Access Memory (RAM),Read-Only Memory (ROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other opticaldisk storage, magnetic disk storage or other magnetic storage devices,flash memory devices (e.g., solid state memory devices), or any otherstorage medium which may be used to carry or store program code in theform of computer-executable instructions or data structures and whichmay be accessed by a general-purpose or special-purpose computer.Combinations of the above may also be included within the scope ofcomputer-readable storage media. Computer-executable instructions mayinclude, for example, instructions and data configured to cause theprocessor 710 to perform or control performance of a certain operationor group of operations as describe in this disclosure.

The communication device 740 may include any component, device, system,or combination thereof that is configured to transmit or receiveinformation over a network. In some embodiments, the communicationdevice 740 may communicate with other devices at other locations, thesame location, or even other components within the same system. Forexample, the communication device 740 may include a modem, a networkcard (wireless or wired), an infrared communication device, a wirelesscommunication device (such as an antenna), and/or chipset (such as aBluetooth device, near-field communication (NFC) device, an 802.6 device(e.g., Metropolitan Area Network (MAN)), a WiFi device, a WiMax device,cellular communication facilities, etc.), and/or the like. Thecommunication device 740 may permit data to be exchanged with a networkand/or any other suitable devices or systems, such as those described inthe present disclosure. For example, when the system 700 is included inthe devices 110, 150, and/or 180 of FIG. 1 , the communication device740 may allow the devices 110, 150, and/or 180 to communicate with oneor more other devices over the network 102 of FIG. 1 and/or othercommunication avenues.

One skilled in the art, after reviewing this disclosure, may recognizethat modifications, additions, or omissions may be made to the system700 without departing from the scope of the present disclosure. Forexample, the system 700 may include more or fewer components than thoseexplicitly illustrated and described.

As used in the present disclosure, the terms “module” or “component” mayrefer to specific hardware implementations configured to perform theactions of the module or component and/or software objects or softwareroutines that may be stored on and/or executed by general purposehardware (e.g., computer-readable media, processing devices, etc.) ofthe computing system. In some embodiments, the different components,modules, engines, and services described in the present disclosure maybe implemented as objects or processes that execute on the computingsystem (e.g., as separate threads). While some of the system and methodsdescribed in the present disclosure are generally described as beingimplemented in software (stored on and/or executed by general purposehardware), specific hardware implementations or a combination ofsoftware and specific hardware implementations are also possible andcontemplated. In this description, a “computing entity” may be anycomputing system as previously defined in the present disclosure, or anymodule or combination of modulates running on a computing system.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, it may be recognized that changesmay be made in form and detail without departing from the scope of thepresent disclosure. Thus, the present disclosure is limited only by theclaims.

Terms used herein and especially in the appended claims (e.g., bodies ofthe appended claims) are generally intended as “open” terms (e.g., theterm “including” should be interpreted as “including, but not limitedto,” the term “having” should be interpreted as “having at least,” theterm “includes” should be interpreted as “includes, but is not limitedto,” etc.).

Additionally, if a specific number of an introduced claim recitation isintended, such an intent will be explicitly recited in the claim, and inthe absence of such recitation no such intent is present. For example,as an aid to understanding, the following appended claims may containusage of the introductory phrases “at least one” and “one or more” tointroduce claim recitations. However, the use of such phrases should notbe construed to imply that the introduction of a claim recitation by theindefinite articles “a” or “an” limits any particular claim containingsuch introduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should be interpreted to mean “at least one”or “one or more”); the same holds true for the use of definite articlesused to introduce claim recitations.

In addition, even if a specific number of an introduced claim recitationis explicitly recited, those skilled in the art will recognize that suchrecitation should be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, means at least two recitations, or two or more recitations).Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” or “one or more of A, B, and C, etc.” isused, in general such a construction is intended to include A alone, Balone, C alone, A and B together, A and C together, B and C together, orA, B, and C together, etc. For example, the use of the term “and/or” isintended to be construed in this manner.

Further, any disjunctive word or phrase presenting two or morealternative terms, whether in the description, claims, or drawings,should be understood to contemplate the possibilities of including oneof the terms, either of the terms, or both terms. For example, thephrase “A or B” should be understood to include the possibilities of “A”or “B” or “A and B.”

However, the use of such phrases should not be construed to imply thatthe introduction of a claim recitation by the indefinite articles “a” or“an” limits any particular claim containing such introduced claimrecitation to embodiments containing only one such recitation, even whenthe same claim includes the introductory phrases “one or more” or “atleast one” and indefinite articles such as “a” or “an” (e.g., “a” and/or“an” should be interpreted to mean “at least one” or “one or more”); thesame holds true for the use of definite articles used to introduce claimrecitations.

Additionally, the use of the terms “first,” “second,” “third,” etc. arenot necessarily used herein to connote a specific order. Generally, theterms “first,” “second,” “third,” etc., are used to distinguish betweendifferent elements. Absence a showing of a specific that the terms“first,” “second,” “third,” etc. connote a specific order, these termsshould not be understood to connote a specific order.

All examples and conditional language recited herein are intended forpedagogical objects to aid the reader in understanding the invention andthe concepts contributed by the inventor to furthering the art, and areto be construed as being without limitation to such specifically recitedexamples and conditions. Although embodiments of the present disclosurehave been described in detail, it should be understood that variouschanges, substitutions, and alterations could be made hereto withoutdeparting from the spirit and scope of the present disclosure.

The previous description of the disclosed embodiments is provided toenable any person skilled in the art to make or use the presentdisclosure. Various modifications to these embodiments will be readilyapparent to those skilled in the art, and the generic principles definedherein may be applied to other embodiments without departing from thespirit or scope of the disclosure. Thus, the present disclosure is notintended to be limited to the embodiments shown herein but is to beaccorded the widest scope consistent with the principles and novelfeatures disclosed herein.

The invention claimed is:
 1. A method for using augmented realitydevices for initiating payment transactions, the method comprising:receiving, by a computer system from a merchant application of anaugmented reality (AR) device accessed by a user, a transaction requestfor a payment transaction to a merchant for an item or a service offeredfor sale to the user in an AR environment, the AR environment presentedto the user via a user interface of the merchant application, the ARenvironment including an AR element displayed to the user thatrepresents the item or service within a physical environment currentlyviewed by the user that does not include a physical version of the itemor the service, wherein the transaction request includes a uniquemerchant identifier identifying the merchant, the item or the service,and a payment amount associated with the payment transaction;communicating, from the computer system to an electronic deviceassociated with the user, an authentication request for authenticatingthe transaction request; in response to receiving an authenticationresponse from the electronic device, authenticating the transactionrequest of the user; and processing the payment transaction using a useraccount associated with the user and a merchant account associated withthe merchant.
 2. The method of claim 1, wherein the processing thepayment transaction comprises transferring funds of the payment amountbetween the user account and the merchant account.
 3. The method ofclaim 1, wherein the AR device is implemented by mixed reality smartglasses.
 4. The method of claim 1, wherein the AR device is owned by themerchant and is not accessed by the user prior to accessing the merchantapplication at the AR device.
 5. The method of claim 1, furthercomprising communicating a confirmation of the authentication of thetransaction request to the merchant to indicate processing of thepayment transaction.
 6. The method of claim 1, wherein theauthentication request indicates at least one verification type to beprovided from the user, the verification type comprising one or more ofa user biometric, a password, and a response to a text message.
 7. Themethod of claim 1, wherein the transaction request indicates a usergesture captured by the AR device during a user selection of the ARelement in the AR environment.
 8. The method of claim 1, wherein thetransaction request is received from a software development kit (SDK)installed in the merchant application.
 9. The method of claim 1, whereina selection of the AR element is received by the merchant application,the selection captured by the merchant application at the AR device, themerchant application associates the transaction request with the uniquemerchant identifier and the payment amount.
 10. A merchant device,comprising: a non-transitory memory storing instructions; and aprocessor configured to execute the instructions to cause the merchantdevice to: receive, from a merchant application at an augmented reality(AR) device, a transaction request to initiate a payment transaction foran item or a service offered by a merchant to a user, the item or theservice presented to the user via a virtual element displayed to theuser in an AR environment of the merchant application at the AR device,wherein the virtual element displayed to the user in the AR environmentsimulates the presence of the item or the service in a physicalenvironment in which the user is currently located and that does notinclude a physical version of the item or the service and upon which theAR environment is projected, wherein the merchant application and themerchant device are both associated with the merchant, and wherein thetransaction request includes a unique merchant identifier identifyingthe merchant, a user identifier identifying the user, the item or theservice, and a payment amount associated with the payment transaction;communicate, from the merchant device to an electronic device associatedwith the user, an authentication request for authenticating thetransaction request; responsive to receiving an authentication responsefrom the electronic device, authenticate the transaction request of theuser; and process the payment transaction using a user accountassociated with the user and a merchant account associated with themerchant.
 11. The merchant device of claim 10, wherein executing theinstructions further causes the merchant device to identify theelectronic device that is associated with the user identifier of theuser, the electronic device being different than the AR device.
 12. Themerchant device of claim 10, wherein the AR device is owned by themerchant and is not accessed by the user prior to accessing the merchantapplication at the AR device.
 13. The merchant device of claim 10,wherein executing the instructions further causes the merchant device tocommunicate a confirmation of the authentication of the transactionrequest to the merchant to indicate processing of the paymenttransaction.
 14. The merchant device of claim 10, wherein theauthentication request indicates at least one verification type to beprovided from the user, the verification type comprising one or more ofa user biometric, a password, and a response to a text message.
 15. Themerchant device of claim 10, wherein a selection of the virtual elementis received by the merchant application, the selection captured by themerchant application at the AR device, the merchant applicationassociates the transaction request with the unique merchant identifierand the payment amount.
 16. A non-transitory machine-readable mediumhaving instructions stored thereon, the instructions executable to causeperformance of operations comprising: receiving, from a merchantapplication of an augmented reality (AR) device accessed by a user, atransaction request for a payment transaction to a merchant for an itemor a service offered for sale to the user in an AR environment, the ARenvironment presented to the user via a user interface of the merchantapplication, the item or service represented by an AR element displayedto the user in the AR environment, wherein the AR environment isoverlayed on a physical environment of the user captured via the ARdevice, wherein the physical environment does not include a physicalversion of the item or the service offered for sale, and wherein thetransaction request comprises a unique merchant identifier identifyingthe merchant, the item or the service, and a payment amount associatedwith the payment transaction; a user interface of the merchantapplication communicating, to an electronic device associated with theuser, an authentication request for authenticating the transactionrequest; in response to receiving an authentication response from theelectronic device, authenticating the transaction request of the user;and processing the payment transaction using a user account associatedwith the user and a merchant account associated with the merchant. 17.The non-transitory machine-readable medium of claim 16, wherein theoperations further comprise identifying the electronic device that isassociated with a user identifier of the user as indicated by the ARdevice, the electronic device being different than the AR device. 18.The non-transitory machine-readable medium of claim 16, wherein the ARdevice is owned by the merchant and is not accessed by the user prior toaccessing the merchant application at the AR device.
 19. Thenon-transitory machine-readable medium of claim 16, wherein theoperations further comprise communicating a confirmation of theauthentication of the transaction request to the merchant to indicateprocessing of the payment transaction.
 20. The non-transitorymachine-readable medium of claim 16, wherein a selection of the ARelement is received by the merchant application, the selection capturedby the merchant application at the AR device, the merchant applicationassociates the transaction request with the unique merchant identifierand the payment amount.